chore: drop trailing keyword block from README#2
Merged
Conversation
Google's search algorithm penalizes obvious keyword stuffing, and a 12-keyword <sub> block at the bottom of a README is the textbook pattern. The buy-intent terms (facebook-scraper, kevinzg, facebook api alternative, instagram-scraper, etc.) already appear naturally throughout the README prose and section headings, which is where search engines actually want to find them. Repo Topics in the About section handle GitHub's own keyword search.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Removes the 12-keyword
<sub>block at the bottom ofREADME.md.Why
Two reasons:
facebook-scraper,kevinzg,facebook api alternative,instagram-scraper— already appears naturally in the README prose and section headings. Google ranks those in-context mentions higher anyway.What handles SEO instead
So no SEO is actually lost — just the spammy-looking footer.
Test plan